Differential online charging for text messages based on network type

ABSTRACT

Systems and methods are disclosed for performing online charging for text messages. One embodiment comprises a system that handles a Mobile Originated (MO) text message. The system receives a send request for the MO text message, and generates an online credit request for the MO text message. The system determines a type of originating network for the MO text message, and inserts an indicator of the originating network type in the online credit request. The system may also determine a type of terminating network for the MO text message, and insert an indicator of the terminating network type in the online credit request. The system then transmits the online credit request to an online charging system to charge for the MO text message.

FIELD OF THE INVENTION

The invention is related to the field of communications and, inparticular, to online charging for text messages that is based on theoriginating network type and/or terminating network type.

BACKGROUND

Text messaging has become a popular mode of communication in many mobile(or wireless) networks. One example of text messaging is Short MessageService (SMS), which is a set of communication protocols allowing theexchange of short text messages (i.e., 160 characters or less) betweendevices. While the term “text message” traditionally referred totext-only messages sent using SMS, it has been extended to includemultimedia messages, such as images, video, sound content, etc. Themultimedia messages may be sent using Multimedia Message Service (MMS)protocol. Often times, mobile users more frequently use text messagingfor communication than voice calls.

Many service providers use flat-rate charging for text messages. Forexample, a sender of a text message may be charged a flat monthly ratefor unlimited text messages. Alternatively, the sender may be charged aflat rate per text message that is sent (e.g., $0.05/message). In orderto optimize revenues, service providers may want more flexibility in howto charge for text messaging.

SUMMARY

Embodiments described herein provide differential online charging fortext messages that depends on the type of originating network for thetext message, and/or the type of terminating network for the textmessage. The conventional flat rate charging for text messages limitsthe pricing options offered by service providers. The online chargingdescribed herein for is not flat rate, but instead depends on the typeof network used by a sender of a text message, and/or the type ofnetwork used by a recipient of the text message. The online chargingdescribed herein may also depend on whether the sender and/or recipientare located in a home network or are roaming. The differential onlinecharging for text messages allows service providers more flexibility inhow to charge for text messaging, which can increase revenues.

One embodiment comprises a system that handles a Mobile Originated (MO)text message. The system includes an interface operable to receive asend request for the MO text message. The system further includes acontroller operable to generate an online credit request for the MO textmessage. The controller is further operable to determine a type oforiginating network for the MO text message, and to insert an indicatorof the originating network type in the online credit request. Theinterface is further operable to transmit the online credit request toan online charging system. The interface is further operable to receivean online credit response from the online charging system, and thecontroller is further operable to accept the MO text message fordelivery if the MO text message is authorized in the online creditresponse.

In another embodiment, the controller is further operable to determineif a sender of the MO text message is roaming, and to insert a roamingindicator for the sender in the online credit request.

In another embodiment, the controller is further operable to determine atype of terminating network for the MO text message, and to insert anindicator of the terminating network type in the online credit request.

In another embodiment, the controller is further operable to determineif a recipient of the MO text message is roaming, and to insert aroaming indicator for the recipient in the online credit request.

In another embodiment, the system is configured to handle a MobileTerminated (MT) text message. The interface is operable to receive asend request for an MT text message. The controller is further operableto generate an online credit request for the MT text message, todetermine a type of network for terminating the MT text message, and toinsert an indicator of the terminating network type in the online creditrequest. The interface is further operable to transmit the online creditrequest to the online charging system. The interface is further operableto receive an online credit response from the online charging system,and the controller is further operable to attempt delivery of the MTtext message to the recipient if the MT text message is authorized inthe online credit response.

In another embodiment, the controller is further operable to determineif a recipient of the MT text message is roaming, and to insert aroaming indicator for the recipient in the online credit request.

In another embodiment, the controller is further operable to determine atype of originating network for the MT text message, and to insert anindicator of the originating network type in the online credit request.

In another embodiment, the controller is further operable to determineif a sender of the MT text message is roaming, and to insert a roamingindicator for the sender in the online credit request.

Other exemplary embodiments may be described below.

DESCRIPTION OF THE DRAWINGS

Some embodiments of the present invention are now described, by way ofexample only, and with reference to the accompanying drawings. The samereference number represents the same element or the same type of elementon all drawings.

FIG. 1 illustrates a communication system in an exemplary embodiment.

FIG. 2 is a flow chart illustrating a method of handling an MO textmessage in an exemplary embodiment.

FIG. 3 is a flow chart illustrating a method of charging for the MO textmessage in an exemplary embodiment.

FIG. 4 is a flow chart illustrating additional steps of handling an MOtext message in an exemplary embodiment.

FIG. 5 is a flow chart illustrating a method of handling an MT textmessage in an exemplary embodiment.

FIG. 6 is a flow chart illustrating a method of charging for an MT textmessage in an exemplary embodiment.

FIG. 7 illustrates a mobile network in another exemplary embodiment.

DESCRIPTION OF EMBODIMENTS

The figures and the following description illustrate specific exemplaryembodiments of the invention. It will thus be appreciated that thoseskilled in the art will be able to devise various arrangements that,although not explicitly described or shown herein, embody the principlesof the invention and are included within the scope of the invention.Furthermore, any examples described herein are intended to aid inunderstanding the principles of the invention, and are to be construedas being without limitation to such specifically recited examples andconditions. As a result, the invention is not limited to the specificembodiments or examples described below, but by the claims and theirequivalents.

FIG. 1 illustrates a mobile network 100 in an exemplary embodiment.Mobile network 100 is operated by a service provider to offer voiceand/or data services to end users. One of the data services offered bythe service provider is text messaging. In this embodiment, mobilenetwork 100 is a hybrid of different technology networks 110-111.Networks 110-111 each represent a different technology network thatprovides service to end user devices (also referred to as User Equipment(UE)). When different technology networks are discussed herein, itrefers to networks that use different signaling interfaces/protocols,different communication interfaces/protocols, or some other incompatibleinterfaces/protocols within their domains that inhibit directcommunication between the networks. For example, network 110 maycomprise a circuit-switched network, such as a Code Division MultipleAccess2000 (CDMA2000) network, while network 111 may comprise apacket-switched network, such as an IP Multimedia Subsystem (IMS)network. In another example, network 110 may comprise a Global Systemfor Mobile Communications (GSM) network, while network 111 may comprisea Long Term Evolution (LTE) network. Although mobile network 100 isshown as a hybrid of two networks in FIG. 1, mobile network 100 mayinclude additional networks not shown.

Each of networks 110-111 is able to transport text messages, such as SMSmessages or MMS messages. Therefore, networks 110-111 are shown as beingconnected to a message center 120. Message center 120 comprises anynetwork element operable to handle the delivery of text messages. Forexample, message center 120 may comprise an SMS Center (SMSC) thatimplements SMS protocol to deliver SMS messages. In another example,message center 120 may comprise an MMS Center (MMSC) that implements MMSprotocol to deliver MMS messages.

Message center 120 includes an interface (I/F) 122 and a controller 124.Interface 122 comprises any device or component that communicates withnetworks 110-111 through signaling protocols. The signaling protocolsdepend on the types of technology used within networks 110-111. Forexample, the signaling protocols may be Session Initiation Protocol(SIP), Mobile Application Part (MAP) protocol, Short MessagePeer-to-Peer (SMPP) protocol, etc. Controller 124 comprises any deviceor component that handles the receipt and delivery of text messages, andhandles charging for the text messages.

In the embodiments described below, when message center 120 handles atext message, it identifies an originating network for the text messageand/or a terminating network for the text message. Message center 120then reports the identity of the originating network and/or theterminating network to an Online Charging System (OCS) 130 so thatcharging for the text message may be based on where the text messageoriginated and/or where the text message is destined.

OCS 130 includes an Online Charging Function (OCF) 132, a Rating Engine(RE) 134, and an Account Balance Management Function (ABMF) 136. OCF 132comprises any system, server, or function operable to manage event-basedonline charging for text messaging (as well as session-based onlinecharging). Rating engine 134 comprises any system, server, or functionoperable to determine a charging rate for a service event based on atariff defined by a service provider. ABMF 136 comprises any system,server, or function operable to maintain an allotment of service units(e.g., a prepaid account) for a prepaid subscriber.

Assume for one embodiment that a text message originates in one ofnetworks 110-111 from a sender. This text message is referred to as aMobile Originated (MO) text message. The text message is encapsulated ina send request of the signaling protocol used in the originatingnetwork. For example, if the originating network is an IMS network, thenthe send request may comprise a SIP MESSAGE. If the originating networkis a GSM network, then the send request may comprise a MAP mo-ForwardSM.The originating network then forwards the send request for the MO textmessage to message center 120.

FIG. 2 is a flow chart illustrating a method 200 of handling the MO textmessage in an exemplary embodiment. The steps of method 200 will bedescribed with reference to message center 120 in FIG. 1, but thoseskilled in the art will appreciate that method 200 may be performed inother networks and systems. The steps of the flow charts describedherein are not all inclusive and may include other steps not shown. Thesteps may also be performed in an alternative order.

In step 202, interface 122 receives the send request for the MO textmessage from the originating network. In response to receiving the MOtext message, controller 124 determines that the sender of the MO textmessage is a prepaid (online) subscriber. Before accepting the MO textmessage, controller 124 seeks permission from OCS 130 to handle the MOtext message. To do so, controller 124 generates an online creditrequest (also referred to as an online debit request) for the MO textmessage in step 204. For example, controller 124 may generate a DiameterRo Credit Control Request (CCR) as an online credit request. Controller124 then populates the online credit request with information on wherethe text message originated and/or where the text message is destined.Thus, controller 124 determines a type of originating network for the MOtext message in step 206. Controller 124 may determine the originatingnetwork type based on the type of signaling used for the send request.For example, if the send request is an SS7 “SMDPP” message, thencontroller 124 determines that the originating network is a CDMA2000network. If the send request is an SS7 MAP “mo-ForwardSM” message, thencontroller 124 determines that the originating network is a GSM/GPRSnetwork. If the send request is a SIP message and the sender is not anLTE subscriber (controller 124 verifies that the sender is not an LTEsubscriber based on a pre-provisioned profile), then controller 124determines that the originating network is an IMS network. If the sendrequest is a SIP message and the sender is an LTE subscriber, thencontroller 124 determines that the originating network is an LTEnetwork.

Additionally in step 206, controller 124 may determine a type ofterminating network for the MO text message. To do so, controller 124may process a pre-provisioned profile for a recipient of the MO textmessage. The profile for the recipient may indicate the terminatingnetwork type for the text message. Alternatively, the profile for therecipient may indicate a subscriber database (e.g., Home SubscriberServer (HSS) or Home Location Register (HLR)) that stores informationabout the recipient, such as the type of network that is serving therecipient.

In step 208, controller 124 inserts an indicator of the originatingnetwork type in the online credit request. Controller 124 may alsoinsert an indicator of the terminating network type in the online creditrequest. In order to insert an indicator of the originating network typeand/or terminating network type in the online credit request, a newfield or parameter may be defined in the charging protocol for theonline credit request. Charging protocols do not presently have a fielddefined for a network type. Therefore, a new field is defined in thecharging protocol for an indicator of the originating network typeand/or an indicator of the terminating network type. As an example, ifthe charging protocol is Diameter, then a new Attribute Value Pair (AVP)is defined for an indicator of the originating network type and/or anindicator of the terminating network type. Interface 122 transmits theonline credit request to OCS 130 in step 210.

FIG. 3 is a flow chart illustrating a method 300 of charging for the MOtext message in an exemplary embodiment. In step 302, OCF 132 receivesthe online credit request from message center 120, and processes theonline credit request to determine that request is for authorization ofa service event (i.e., the MO text message). OCF 132 is an event-basedcontrol function that is tasked with charging for service events, suchas a text message. Therefore, OCF 132 transmits charging information torating engine 134 to determine a charging rate for the MO text message.The charging information includes the indicator of the originatingnetwork type and/or the indicator of the terminating network type.Rating engine 134 determines the charging rate for the MO text messagein step 304, which is a price or cost of sending the MO text message(e.g., $0.05/message). Rating engine 134 may determine the charging ratebased on a predefined rating table that takes into consideration theoriginating network type, the terminating network type, time of day orday of the week, roaming versus non-roaming, or other conditions. Ratingengine 134 then reports the charging rate to OCF 132.

With the charging rate for the MO text message, OCF 132 communicateswith ABMF 136 to determine if the account balance for the sender issufficient for the charging rate of the MO text message in step 306. Ifthe account balance for the sender is sufficient, then OCF 132authorizes the MO text message and debits the account of the sender inABMF 136 in step 308. OCF 132 generates an online credit response, suchas a Diameter Credit Control Answer (CCA), and then inserts anindication in the online credit response that the MO text message isauthorized. OCF 132 then sends the online charging response to messagecenter 120 in step 310.

If the account balance for the sender is insufficient, then OCF 132 maydeny the MO text message in step 312. OCF 132 then inserts an indicationin the online credit response that the MO text message is denied, andsends the online charging response to message center 120 in step 314.OCF 132 may alternatively notify the sender that the account balance isinsufficient, and attempt to obtain payment from the sender.

In FIG. 2, interface 122 of message center 120 receives the onlinecredit response from OCS 130 in step 212. If the MO text message isauthorized in the online credit response, then controller 124 acceptsthe MO text message for delivery in step 214. If the MO text message isnot authorized in the online credit response, then controller 124 deniesthe MO text message in step 216.

In addition to or as an alternative to charging based on the networktype of the originating and/or terminating network, the MO text messagemay be charged based on whether the sender and/or recipient of the MOtext message is located in a home network or is roaming FIG. 4 is a flowchart illustrating the additional steps of handling the MO text messagein an exemplary embodiment. Before sending the online credit request toOCS 130 (step 210), controller 124 determines whether the sender of theMO text message is roaming in step 402. In other words, controller 124determines whether the originating network for the MO text message is ahome network or a roaming network for the sender. To determine whetherthe sender is roaming, controller 124 may process a network address in arouting layer of the send request. For example, if the send request isin SS7 protocol, then controller 124 may identify a network address inthe Signaling Connection Control Part (SCCP) layer (e.g., “Calling PartyAddress”) of the SS7 message. Controller 124 then determines if thecalling party address belongs to a home network or a roaming (foreign)network. After determining the roaming/non-roaming status of the sender,controller 124 inserts a roaming indicator for the sender in the onlinecredit request that indicates whether the sender is roaming ornon-roaming in step 404.

Also, controller 124 may determine whether the recipient of the MO textmessage is roaming in step 406. In other words, controller 124determines whether the terminating network for the MO text message is ahome network or a roaming network for the recipient. To do so,controller 124 may query a subscriber database (e.g., HSS or HLR) forthe recipient to determine the network address of the recipient.Controller 124 then determines if the network address provided by thesubscriber database belongs to a home network or a roaming (foreign)network. After determining the roaming/non-roaming status of the sender,controller 124 inserts an indicator for the recipient in the onlinecredit request that indicates whether the recipient is roaming ornon-roaming in step 408.

OCS 130 may then process this additional information (as shown in FIG.3) to determine how much to charge for the MO text message.

A similar process as above is used in delivering a Mobile Terminated(MT) text message. Assume that the MT text message is addressed to arecipient being served by one of networks 110-111. The MT text messageis routed to message center 120 in a send request much as describedabove.

FIG. 5 is a flow chart illustrating a method 500 of handling the MT textmessage in an exemplary embodiment. The steps of method 500 will bedescribed with reference to message center 120 in FIG. 1, but thoseskilled in the art will appreciate that method 500 may be performed inother networks and systems.

In step 502, interface 122 receives the send request for the MT textmessage. In response to receiving the MT text message, controller 124determines that the recipient of the MT text message is a prepaid(online) subscriber. Before attempting to deliver the MT text message tothe recipient, controller 124 seeks permission from OCS 130. Controller124 generates an online credit request for the MT text message in step504. Controller 124 then populates the online credit request withinformation on where the text message is destined and/or where the textmessage originated as described below.

Controller 124 determines a type of terminating network for the MT textmessage in step 506. Controller 124 may determine the terminatingnetwork type by querying a subscriber database. If the recipient is anLTE subscriber or dual mode (SS7/IMS) subscriber, then controller 124may query an HSS to determine the IMSUserState and S-CSCFName for therecipient. If the HSS indicates that the recipient is present in an IMSnetwork, then controller 124 determines that terminating network type isan LTE network if the recipient is an LTE subscriber as per apre-provisioned profile. If the recipient is not an LTE subscriber asper the pre-provisioned profile, then controller 124 determines thatterminating network type is an IMS network. If the recipient is aCDMA2000 subscriber as per the pre-provisioned profile, then controller124 queries a CDMA HLR using a SS7 ‘SMSREQ’ message. If the smsrequest[ACK] from the HLR returns a “smsaddr”, then controller 124 determinesthat the terminating network is a CDMA2000 network. If the recipient isa GSM/UMTS subscriber as per the pre-provisioned profile, thencontroller 124 queries a GSM/UMTS HLR using an SS7 MAPsendRoutingInfoForSM message. If the sendRoutingInfoForSM-res from theHLR includes a “networkNode-Number”, then controller 124 determines thatthe terminating network is a GSM network.

Additionally in step 506, controller 124 may determine a type oforiginating network for the MT text message. Controller 124 may processa type of signaling protocol used in the originating network todetermine an originating network type. Alternatively, controller 124 mayprocess a pre-provisioned profile for the sender of the MT text message.The profile for the sender may indicate the originating network type forthe text message.

In step 508, controller 124 to inserts an indicator of the terminatingnetwork type in the online credit request. Controller 124 may alsoinsert an indicator of the originating network type in the online creditrequest. As in the MO embodiment, a new field or parameter may bedefined in the charging protocol for the online credit request toinclude an indicator of the terminating network type and/or an indicatorof the originating network type. In step 510, interface 122 transmitsthe online credit request to OCS 130.

FIG. 6 is a flow chart illustrating a method 600 of charging for the MTtext message in an exemplary embodiment. In step 602, OCF 132 receivesthe online credit request from message center 120, and processes theonline credit request to determine that request is for authorization ofa service event (i.e., the MT text message). OCF 132 transmits charginginformation to rating engine 134 to determine a charging rate for the MTtext message. The charging information includes the indicator of theterminating network type and/or the indicator of the originating networktype. Rating engine 134 determines the charging rate for the MT textmessage in step 604, which is a price or cost of delivering the MT textmessage (e.g., $0.05/message). Rating engine 134 then reports thecharging rate to OCF 132.

With the charging rate for the MT text message, OCF 132 communicateswith ABMF 136 to determine if the account balance for the recipient issufficient for the charging rate of the MT text message in step 606. Ifthe account balance for the recipient is sufficient, then OCF 132authorizes the MT text message and debits the account of the recipientin step 608. OCF 132 generates an online credit response, such as aDiameter CCA, and inserts an indication in the online credit responsethat the MT text message is authorized. OCF 132 then sends the onlinecharging response to message center 120 in step 610.

If the account balance for the recipient is insufficient, then OCF 132may deny the MT text message in step 612. OCF 132 then inserts anindication in the online credit response that the MT text message isdenied, and sends the online charging response to message center 120 instep 614.

In FIG. 5, interface 122 of message center 120 receives the onlinecredit response from OCS 130 in step 512. If the MT text message isauthorized in the online credit response, then controller 124 attemptsdelivery of the MT text message to the recipient in step 514. If the MTtext message is not authorized in the online credit response, thencontroller 124 discards the MT text message in step 516.

In addition to or as an alternative to charging based on the networktype of the originating and/or terminating network, the MT text messagemay be charged based on whether the recipient and/or sender of the MTtext message is located in a home network or is roaming (see FIG. 4).

Message center 120 as described above allows for differential chargingfor text messages that depends on the type of originating network forthe text message, and/or the type of terminating network for the textmessages. Instead of flat rate charging for text messages, the chargingdescribed herein depends on the type of network used by a sender of atext message, and/or the type of network used by a recipient of the textmessage. Therefore, service providers have more flexibility in how tocharge for text messaging, which can increase revenues.

EXAMPLE

FIG. 7 illustrates a mobile network 700 in another exemplary embodiment.In this embodiment, mobile network 700 is a hybrid of an IMS network 710and a CDMA2000 network 711, which are different technology networks. IMSnetwork 710 is connected to SMS Center (SMSC) 720, and CDMA2000 network711 is connected to SMSC 721. SMSCs 720-721 are connected to an OnlineCharging System (OCS) 730.

In this example, IMS network 710 serves User Equipment (UE) 740 of asender of a SMS message. The SMS message is addressed to a recipientthat is served by CDMA2000 network 711 (through UE 750). To send the SMSmessage, UE 740 of the sender encapsulates the SMS message in a SIPMESSAGE, such as in the RP-DATA (e.g., RP-User-Data field) of the SIPMESSAGE. UE 740 then transmits the SIP MESSAGE to IMS network 710, whichforwards the SIP MESSAGE to SMSC 720.

From the point of view of SMSC 720, the SMS message (in the SIP MESSAGE)is a MO message. In response to receiving the MO SMS message, SMSC 720determines that the sender of the MO SMS message is a prepaid (online)subscriber. Before accepting the MO SMS message, SMSC 720 seekspermission from OCS 730 to handle the MO SMS message. To do so, SMSC 720generates a Diameter Ro Credit Control Request (CCR) for the MO SMSmessage. SMSC 720 then determines a type of originating network for theMO SMS message, such as by processing the incoming message protocoltype. In this example, the originating network type is “IMS”. SMSC 720also determines a type of terminating network for the MO SMS message.SMSC 720 may query a local database or a subscriber database (e.g.,HSS/HLR) to determine the terminating network type. The terminatingnetwork type in this example is CDMA2000. SMSC 720 then inserts anindicator of the originating network type (i.e., IMS) and an indicatorfor the terminating network type (i.e., CDMA2000) in the Diameter CCR. Anew AVP is defined in the Diameter protocol for these indicators.Diameter has an AVP defined for a “protocol”. However, protocols may notnecessarily indicate a type of network. For instance, SIP may be used inIMS networks and LTE networks. Thus, a protocol indicator does notspecify a network type. The new Diameter AVP defined herein actuallyindicates/specifies the network type for an originating network and/orterminating network. SMSC 720 then transmits the Diameter CCR to OCS730.

OCS 730 processes the Diameter CCR to determine that request is forauthorization of an MO SMS message. OCS 730 determines a charging ratefor the MO SMS message based on the indicator of the originating networktype and/or the indicator of the terminating network type. If theaccount balance for the sender is sufficient for the charging rate ofthe MO SMS message, then OCS 730 authorizes the MO SMS message anddebits the account of the sender. OCS 730 then returns a Diameter CreditControl Answer (CCA) to SMSC 720 with authorization for the MO SMSmessage. Because the MO SMS message was authorized by OCS 730, SMSC 720accepts the MO SMS message for delivery. SMSC 720 may then performstore-and-forward processing of the MO SMS message as defined by the SMSprotocols.

Because the SMS message is intended for the recipient in CDMA2000network 711, SMSC 720 forwards the SMS message to SMSC 721. SMSC 720 mayforward the SMS message in a SIP MESSAGE, or in a protocol used withinSMSC 721. From the point of view of SMSC 721, the SMS message is an MTmessage.

In response to receiving the MT SMS message, SMSC 721 determines thatthe recipient of the MT SMS message is a prepaid (online) subscriber.Before attempting to deliver the MT SMS message to the recipient, SMSC721 seeks permission from OCS 730. SMSC 721 generates a Diameter CCR forthe MT SMS message. As in the MO example, SMSC 721 determines theterminating network type (CDMA2000) and the originating network type(IMS) for the MT SMS message. SMSC 721 then inserts an indicator of theterminating network type (i.e., CDMA2000) and an indicator for theoriginating network type (i.e., IMS) in the Diameter CCR, and transmitsthe Diameter CCR to OCS 730.

OCS 730 processes the Diameter CCR to determine that request is forauthorization of an MT SMS message. OCS 730 determines a charging ratefor the MT SMS message based on the indicator of the originating networktype and/or the indicator of the terminating network type. If theaccount balance for the recipient is sufficient for the charging rate ofthe MT SMS message, then OCS 730 authorizes the MT SMS message anddebits the account of the recipient. OCS 730 then returns a Diameter CCAto SMSC 721 with authorization for the MT SMS message. Because the MTSMS message was authorized by OCS 730, SMSC 721 initiatesstore-and-forward processing of the MT SMS message to attempt deliveryto UE 750 of the recipient over CDMA2000 network 711.

Any of the various elements shown in the figures or described herein maybe implemented as hardware, software, firmware, or some combination ofthese. For example, an element may be implemented as dedicated hardware.Dedicated hardware elements may be referred to as “processors”,“controllers”, or some similar terminology. When provided by aprocessor, the functions may be provided by a single dedicatedprocessor, by a single shared processor, or by a plurality of individualprocessors, some of which may be shared. Moreover, explicit use of theterm “processor” or “controller” should not be construed to referexclusively to hardware capable of executing software, and mayimplicitly include, without limitation, digital signal processor (DSP)hardware, a network processor, application specific integrated circuit(ASIC) or other circuitry, field programmable gate array (FPGA), readonly memory (ROM) for storing software, random access memory (RAM), nonvolatile storage, logic, or some other physical hardware component ormodule.

Also, an element may be implemented as instructions executable by aprocessor or a computer to perform the functions of the element. Someexamples of instructions are software, program code, and firmware. Theinstructions are operational when executed by the processor to directthe processor to perform the functions of the element. The instructionsmay be stored on storage devices that are readable by the processor.Some examples of the storage devices are digital or solid-statememories, magnetic storage media such as a magnetic disks and magnetictapes, hard drives, or optically readable digital data storage media.

Although specific embodiments were described herein, the scope of theinvention is not limited to those specific embodiments. The scope of theinvention is defined by the following claims and any equivalentsthereof.

We claim:
 1. A system comprising: a message center for text messagingthat is coupled to a plurality of mobile networks which comprisedifferent technology networks, wherein the message center includes: aninterface operable to receive a send request for a Mobile Originated(MO) text message from an originating mobile network; and a controlleroperable to generate an online credit request for the MO text message,to determine a technology network type for the originating mobilenetwork where the MO text message originated, and to insert an indicatorof the technology network type for the originating mobile network in theonline credit request; the interface is further operable to transmit theonline credit request to an online charging system.
 2. The system ofclaim 1 wherein: the controller is further operable to determine if asender of the MO text message is roaming, and to insert a roamingindicator for the sender in the online credit request.
 3. The system ofclaim 1 wherein: the controller is further operable to determine atechnology network type for a terminating mobile network where the MOtext message is destined, and to insert an indicator of the technologynetwork type for the terminating mobile network in the online creditrequest.
 4. The system of claim 3 wherein: the controller is furtheroperable to determine if a recipient of the MO text message is roaming,and to insert a roaming indicator for the recipient in the online creditrequest.
 5. The system of claim 1 wherein: the controller is furtheroperable to insert the indicator of the technology network type for theoriginating mobile network in a new field of the online credit request.6. A method comprising: receiving, in a message center for textmessaging, a send request for a Mobile Originated (MO) text message froman originating mobile network, wherein the message center is coupled toa plurality of mobile networks which comprise different technologynetworks; generating an online credit request for the MO text message inthe message center; determining, in the message center, a technologynetwork type for the originating mobile network where the MO textmessage originated; inserting an indicator of the technology networktype for the originating mobile network in the online credit request;and transmitting the online credit request from the message center to anonline charging system.
 7. The method of claim 6 further comprising:determining if a sender of the MO text message is roaming; and insertinga roaming indicator for the sender in the online credit request.
 8. Themethod of claim 6 further comprising: determining a technology networktype for a terminating mobile network where the MO text message isdestined; and inserting an indicator of the technology network type forthe terminating mobile network in the online credit request.
 9. Themethod of claim 8 further comprising: determining if a recipient of theMO text message is roaming; and inserting a roaming indicator for therecipient in the online credit request.
 10. The method of claim 6wherein inserting an indicator of the technology network type for theoriginating mobile network in the online credit request comprises:inserting the indicator of the technology network type for theoriginating mobile network in a new field of the online credit request.